---
---
<!DOCTYPE html> 
<html lang=en>
<head>
	<meta charset=utf-8>

	<link rel="stylesheet" type="text/css" href="{{ site.baseurl }}/common/css/stylesheet.css"/>
	<link rel="stylesheet" href="{{ site.baseurl }}/common/css/stylesheet-fonts.css" type="text/css" charset="utf-8">
	<link rel="icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
	<link rel="shortcut icon" href="{{ site.baseurl }}/common/css/favicon.ico" type="image/x-icon">
	<title>Magento Commerce Release Notes (1.14 and later)</title>

</head>

<body>
<a name="top"></a>

<img src="{{ site.baseurl }}/common/images/m1x/m1xheader.png" width="1024" alt="header" />

  
<h1>Magento Commerce Release Notes (1.14 and later)</h1>


<div class="toc"> <h4 class="toc">Contents</h4>
<p>These Release Notes contain the following information:</p>
<ul><li><a href="#upgrade">Important Upgrade Information</a></li>

	<li><a href="#ee114-11438">Magento Commerce 1.14.3.8 Release Notes</a></li>
	<li><a href="#ee114-11437">Magento Commerce 1.14.3.7 Release Notes</a></li>
	<li><a href="#ee114-11436">Magento Commerce 1.14.3.6 Release Notes</a></li>
	<li><a href="#ee114-11435">Magento Commerce 1.14.3.5 Release Notes</a></li>
	<li><a href="#ee114-11434">Magento Commerce 1.14.3.4 Release Notes</a></li>
	<li><a href="#ee114-11433">Magento Commerce 1.14.3.3 Release Notes</a></li>
	<li><a href="#ee114-11432">Magento Commerce 1.14.3.2 Release Notes</a></li>
	<li><a href="#ee114-11431">Magento Commerce 1.14.3.1 Release Notes</a></li>
	<li><a href="#ee114-11430">Magento Commerce 1.14.3.0 Release Notes</a></li>
<li><a href="http://docs.magento.com/m1/ee/user_guide/magento/release-notes-ee-1.14.2.html" target="_blank">Magento Commerce 1.14.2.0 Release Notes</a></li>
<li><a href="http://docs.magento.com/m1/ee/user_guide/magento/release-notes-ee-1.14.1.html" target="_blank">Magento Commerce 1.14.1.0 Release Notes</a></li>
<li><a href="#ee114-11401">Magento Commerce 1.14.0.1 Release Notes</a></li>
<li><a href="#ee114-patches">Recent Patches</a></li>
<li><a href="#ee114-11400">Magento Commerce 1.14.0.0 Release Notes</a></li>
<li><a href="#oss">Open Source Software Licensing Agreements</a></li>
</ul>

</div> 



<h2 id="upgrade">Important Upgrade Information</h2>
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-important.png" alt="important" align="left" width="40"><span><strong>Important</strong>: Use Magento Commerce 1.14.3.0或更新 for <em>all new Magento Commerce installations and upgrades</em> to get the latest fixes, features, and security updates.</span></div>

<h2 id="ee114-11438">Magento Commerce 1.14.3.8 Release Notes</h2>
<p>This version (or patch SUPEE-10570, which applies to older versions of Magento) provides resolution of multiple critical security issues. These critical security issues include remote code execution, cross-site scripting, and cross-site request forgery issues. We recommend upgrading your Magento store to this latest version.  See  <a href="https://magento.com/security/patches/supee-10415" target="_blank">Magento Security Center</a> for a comprehensive discussion of these issues.</p>

<h3>Fixed issues and enhancements</h3>
<ul>
<li><b>Changed Magento Admin to support recent USPS shipping changes</b>. On February 23, 2018, USPS removed APIs that support the creation of shipping labels without postage. In response, we’ve removed this functionality from the Magento Admin. Consequently, you cannot create and print shipping labels that do not have postage applied.  </li>

<li><b>Updated copyright to 2018</b>.</li>
</ul>

<h3>Known issues</h3>

<p>These two known issues are associated with the use of HTML tags within a product’s SKU attribute:</p>

<ul>
<li>If you try to import products that contain HTML tags in the SKU attribute, Magento displays this error  at the data validation stage (that is, when you click <b>Check data</b>):  <code>Invalid value in SKU column. HTML tags are not allowed</code>.</li>


<li>If you try to create  or edit a product in the Admin panel and the product’s SKU attribute value contains HTML tags, Magento throws this error when you try to save the product: <code>HTML tags are not allowed in SKU attribute</code>. </li>
</ul>


<h2 id="ee114-11437">Magento Commerce 1.14.3.7 Release Notes</h2>
<p>This patch (SUPEE-10415) provides resolution of multiple critical security issues. These critical security issues include remote code execution, cross-site scripting, and cross-site request forgery issues. We recommend upgrading your Magento store to this latest version.  See  <a href="https://magento.com/security/patches/supee-10415" target="_blank">Magento Security Center</a> for a comprehensive discussion of these issues.</p>

<h3>Fixed issues</h3>

<ul>


<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9842" target="_blank">MPERF-9842</a>.-->Magento no longer displays the “Invalid Secret Key. Please refresh the page.” message when a user loads the Admin.</li>


<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9685" target="_blank">MPERF-9685</a>.-->The one-page checkout page now displays the following message when a customer checks out an order for which no amount is due: <b>No payment information required</b>. Magento versions prior to 1.14.3.3 included this message, but it was missing from v1.14.3.3.</li>


<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9843" target="_blank">MPERF-9843</a>.-->We’ve fixed a typo in the patch header information. (<code>autocomplete="new-pawwsord”</code> is now <code>autocomplete="new-password”</code>.)
</li>
</ul>

<h3>Known issue</h3>
<p><b>Issue:</b> Magento displays a  "404: Page Not Found" error from the <code>errors/</code> directory after upgrading to SUPEE-10415. This issue occurs only in Magento installations that run certain third-party extensions.</p>

<p><b>Description:</b> Magento is not properly logging PHP warnings that occur early during page initialization. Instead, of logging the error and continuing operation, Magento generates a 404 page. (Previously, Magento logged these warnings in the system.log file, and execution would continue as usual.)</p>

<p><b>Workaround:</b> Confirm that there are no PHP warnings generated by any of the extensions or customizations.</p>




<h3>Notes</h3>

<ul><li> We no longer support custom file extensions for <code>Mage::log()</code>. Supported file extensions include <code>.log</code>, <code>.txt</code>, <code>.html</code>, <code>.csv</code>. For more information, navigate to <b>Developers > Log Settings</b> from the Admin. Magento displays this comment: <b>Logging from Mage::log(). File is located in {{ base_dir }}/var/log. Allowed file extensions: log, txt, html, csv.</b> </li>

<li>Passwords for new users are now limited to  256 characters. If a new user enters a password that exceeds 256 characters, Magento displays this message: <b>Please enter a password with at most 256 characters</b>. </li>
</ul>



<h2 id="ee114-11436">Magento Commerce 1.14.3.6 Release Notes</h2>
<p>This patch (SUPEE-10266) provides resolution of multiple critical security issues and several functional fixes. These critical security issues include remote code execution, cross-site scripting, and cross-site request forgery issues. We recommend upgrading your Magento store to this latest version.  See  <a href="https://magento.com/security/patches/supee-10266" target="_blank">Magento Security Center</a> for a comprehensive discussion of these issues.</p>




<p><a href="https://magento.com/security/patches/supee-10266" target="_blank">SUPEE-10266</a> includes a fix for MPERF-9685. This fix is not included in release 1.14.3.6. However, in some cases,  SUPEE-10266 can cause issues in the checkout process. Specifically, if a customer enables the  Add gift options checkbox during checkout, the checkout process will not progress beyond the payments step. </p>

<p><b>Note</b>: We’ve released patch SUPEE-10348 to address issues with checkout that some users experienced after applying SUPEE-10266. SUPEE-10348 must be applied on top of SUPEE-10266. Note that if you are experiencing issues in checkout when using gift options, SUPEE-10348 should resolve these issues. </p>



<p>If you are currently affected by this issue, you can workaround this issue by restore these two files to the pre-patch versions:</p>
 
<p><code>app/design/frontend/enterprise/default/template/giftcardaccount/onepage/payment/scripts.phtml</code></p>

<p><code>app/design/frontend/rwd/enterprise/template/giftcardaccount/onepage/payment/scripts.phtml</code></p>


<!-- <a href="https://jira.corp.magento.com/browse/MPERF-9726" target="_blank">MPERF-9726</a>.-->We’ve also fixed an issue where uploaded images were twice their original size after you applied SUPEE-9767 v2.


<h2 id="ee114-11435">Magento Commerce 1.14.3.5 Release Notes</h2>
We have skipped release 1.14.3.5. 

<h2 id="ee114-11434">Magento Commerce 1.14.3.4 Release Notes</h2>
 <p>This patch (SUPEE-9767 version 2) addresses both security and functional issues discovered when using the <code>SUPEE-9767</code> patch. We recommend upgrading your Magento store to this latest version.  

 Here are your upgrade options:


<ul><li>Upgrade to Magento Commerce 1.14.3.4. You don’t need to revert any patches or install SUPEE-9767 version 2 as version 2 is already included in the 1.14.3.4 release. </li>

<li>If you’ve already installed SUPEE-9767 version 1, you can either: 

	<ul>
	<li>Upgrade to  Magento Commerce 1.14.3.4, or</li>

	<li>revert SUPEE-9767 version 1, then install SUPEE-9767 version 2.</li>
	</ul>
	</li>



<li>If you haven’t installed SUPEE-9767 version 1, you can either: 

	<ul><li>Upgrade to Magento Commerce 1.14.3.4, or </li>

	<li>install SUPEE-9767 version 2.
	</li></ul>

</ul>







See  <a href="https://magento.com/security/patches/supee-9767" target="_blank">Magento Security Center</a> for a comprehensive discussion of these security issues.</p>

 <p>This release also provides support for the following functional issues: </p>

<h3>General fixes</h3>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9584" target="_blank">MPERF-9584</a>. -->We’ve added a missing <code>form_key</code> to the enterprise shipping template (<code>app/design/frontend/enterprise/default/template/checkout/onepage/shipping.phtml</code>).</li>

	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9591" target="_blank">MPERF-9591</a>.-->We’ve restored missing <code>strip_tags</code> functionality in the checkout JavaScript.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9583" target="_blank">MPERF-9583</a> .-->We’ve changed how Magento validates form keys during the generic five-step checkout process. Previously, customer registration failed during standard checkout processing if form key authentication was enabled.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9589" target="_blank">MPERF-9589</a>. -->You can now successfully add a product to the shopping cart when FPC (Full Page Cache) is enabled. Previously, when FPC was enabled, adding a product to the cart resulted in an empty cart.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9585" target="_blank">MPERF-9585</a>. -->Magento now displays the <code>Allow_symlinks</code> message in the Admin message area as expected.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9594" target="_blank">MPERF-9594</a>.  -->Magento now preserves the background transparency of uploaded images as expected. Previously, transparency was lost after the image was uploaded, resulting in an unusable image.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9635" target="_blank">MPERF-9635</a>.  --> You can now use Checkout with Multiple Addresses when checkout form validation is enabled.</li>

	</ul>

<h3>Installation</h3>
	<ul>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9581" target="_blank">MPERF-9581</a>. --> The Allow symlinks option is now disabled during installation or upgrade processes. Previously, when you changed the Allow symlinks setting to true in the database before upgrading and then installing the patch, this option remained enabled,  but you could no longer access it from the Admin panel.</li>
</ul>

This patch is available from <a href="https://magento.com/tech-resources/download" target="_blank">Magento Tech Resources</a>.</p>









<h2 id="ee114-11433">Magento Commerce 1.14.3.3 Release Notes</h2>
 <p>This patch provides resolution of multiple critical security issues. These critical issues include remote code execution for authenticated Admin users, access control bypass, and cross-site request forgery issues. See  <a href="https://magento.com/security/patches/supee-9767" target="_blank">Magento Security Center</a> for a comprehensive discussion of these issues.</p>
 
 <p>This release also provides support for the following issue: </p>

 <p><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9553" target="_blank">MPERF-9553</a>  -->Support for PayPal's update to its Instant Payment Notification (IPN) server URL. PayPal provides more information about this feature in <a href="https://www.paypal-knowledge.com/infocenter/index?page=content&widgetview=true&id=FAQ1916&viewlocale=en_US" target="_blank">IPN Verification Postback to HTTPS Microsite</a>. This update is essential for retaining uninterrupted service after June 30.</p>

 <p><code>SUPEE-8167</code>, an older patch that also contains this fix, was added on May 8, 2017, and is available from <a href="https://magento.com/tech-resources/download" target="_blank">Magento Tech Resources</a>.</p>

<h3>Known Issues</h3>
<p>This patch/release has known issues. Please see <a href="https://magento.com/security/patches/supee-9767" target="_blank">SUPEE-9767</a> for updates.</p>

<p><b>Note:</b> Before applying this patch or updating to this release, disable the <b>Symlinks</b> setting in <b>System > Configuration > Advanced > Developer > Enable Symlinks</b>. If the <b>Symlinks</b> setting is enabled, it will override your configuration file settings. If that override occurs, you will need to directly modify the database to change those settings.</p>

<h2 id="ee114-11432">Magento Commerce 1.14.3.2 Release Notes</h2>
<p>This patch addresses the following issues:</p>
<ul><li>Removal of vulnerability with the Zend framework <code>Zend_Mail</code> library. For more information, see <a href="https://magento.com/security/patches/supee-9652" target="_blank">Magento Security Center</a>. </li>
	<li>Updated the copyright year to 2017.</li></ul>


<h2 id="ee114-11431">Magento Commerce 1.14.3.1 Release Notes</h2>
<p>This patch addresses the following issues:</p>
<ul><!-- <li><a href="https://jira.corp.magento.com/browse/MPERF-9229" target="_blank">MPERF-9229</a>. Configurable swatches work as expected.</li> -->
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9221" target="_blank">MPERF-9221</a>.  -->We restored the old tax calculation algorithm for shipping charges. The patch to apply new calculation will be available on request.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9269" target="_blank">MPERF-9269</a> .-->Resolved an issue with setting the session lifetime to 0.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9233" target="_blank">MPERF-9233</a> .--> The monthly cron job that cleans up the table that contains IP addresses and passwords runs properly.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9266" target="_blank">MPERF-9266</a>. --> All configurable product images are imported.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9219" target="_blank">MPERF-9219</a>. --> You no longer get an exception due to an undefined <code>addCrumbs()</code> method call.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9218" target="_blank">MPERF-9218</a>.  -->Resolved the error <code>Notice: Undefined index: session_expire_timestamp</code> when accessing the storefront.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9217" target="_blank">MPERF-9217</a>. --> Values for drop-down label values are saved correctly.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9216" target="_blank">MPERF-9216</a>. --> The "Price as configured" for bundle products displays correctly in the shopping cart.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9215" target="_blank">MPERF-9215</a>.  -->Auto-generated passwords are sent to new customers as expected.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9214" target="_blank">MPERF-9214</a>.  -->The method <code>Mage_Api_Model_Server_Handler_Abstract::processingMethodResult()</code> accepts scalar and array values.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9213" target="_blank">MPERF-9213</a>.  -->The default MySQL Full-Text search works as expected; it no longer returns all products.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-9184" target="_blank">MPERF-9184</a>.  -->Prevented a potential <a href="https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)_Prevention_Cheat_Sheet" target="_blank">Cross-Site Request Forgery (CSRF)</a> vulnerability by changing the form key when a customer signs out of the storefront.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8444" target="_blank">MPERF-8444</a>.  -->Prevented a potential <a href="https://www.owasp.org/index.php/Cross-site_Scripting_(XSS)" target="_blank">Cross-Site Scripting (XSS)</a> vulnerability when adding a category.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5893" target="_blank">MPERF-5893</a>.  -->Catalog price rules return the correct price.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5352" target="_blank">MPERF-5352</a>.  -->Indexers now update all products instead of skipping the last product updated.</li>

</ul>

<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-note.png" alt="note" align="left" width="40"><span><strong>注意</strong>: You currently <em>cannot</em> upgrade to this version using Magento Connect Manager. We expect to resolve this issue soon.</div>


<h2 id="ee114-11430">Magento Commerce 1.14.3.0 Release Notes</h2>
<p>See the following sections for information about this release:</p>

<ul><li><a href="#ee114-11430-highlights">Highlights</a></li>
<li><a href="#ee114-1430security">Security Enhancements</a></li>
<li><a href="#ee114-1430security-upgrade">Check for <code>.swf</code> File After Upgrade</a></li>
<li><a href="#ee114-1430back">Backward-Incompatible Changes</a></li>
<li><a href="#ee114-11430-changes">Changes</a></li>
<li><a href="#ee114-1430fixes">Fixes</a></li>

<h3 id="ee114-11430-highlights">Highlights</h3>
<p>Magento Commerce 1.14.3 delivers more than 120 quality improvements, as well as support for PHP 5.6 in addition to PHP 5.4 and 5.5. <!-- <a href="https://jira.corp.magento.com/browse/MPERF-7852" target="_blank">MPERF-7852</a> --></p>

<h3 id="ee114-1430security">Security Enhancements</h3>
<p>We addressed the following security issues in this release:</p>
<ul><li><a href="#ee114-1430security-general">General security enhancements</a></li>
	<li><a href="#ee114-1430security-pwd">Password enhancements<a></li>
</ul>

<h4 id="ee114-1430security-general">General security enhancements</h4>
<p>For more information about these security enhancements, see <a href="https://magento.com/security/patches/supee-8788" target="_blank">our Security Center article</a>.</p>
<p>Patches for major security issues in earlier versions of the Magento software are available in the Magento Commerce customer portal.</p>

<p>Details about security fixes:</p>
<ul><li>Resolved a potential SQL injection (Zend Framework issue)</li>
	<li>Resolved a cache poisoning issue</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7714" target="_blank">MPERF-7714</a> --> We now provide better protection against path exploits.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8444" target="_blank">MPERF-8444</a>. --> Resolved a potential <a href="https://www.owasp.org/index.php/XSS" target="_blank">cross-site scripting (XSS)</a> vulnerability when adding a category.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8968" target="_blank">MPERF-8968</a>. --> Resolved a potential XSS vulnerability that affected the Magento server's request URI.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/APPSEC-1488" target="_blank">APPSEC-1488</a>. --> Resolved a potential XSS vulnerability in invitations.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8077" target="_blank">MPERF-8077</a> --> You can no longer cause out-of-memory errors on the Magento server by flooding it with images that have incorrect dimensions.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8059" target="_blank">MPERF-8059</a> --> The Magento Admin Panel login page now renders in HTTPS if you configured the Magento server for HTTPS.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8050" target="_blank">MPERF-8050</a> --> We added the <a href="https://www.owasp.org/index.php/List_of_useful_HTTP_headers" target="_blank"><code>nosniff</code> header</a> to our <code>.htaccess</code> files.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7516" target="_blank">MPERF-7516</a> --> Magento no longer uses Adobe Flash for uploads.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8192" target="_blank">MPERF-8192</a>, <a href="https://jira.corp.magento.com/browse/MPERF-7860" target="_blank">MPERF-7860</a>, <a href="https://jira.corp.magento.com/browse/MPERF-7859" target="_blank">MPERF-7859</a>, <a href="https://jira.corp.magento.com/browse/MPERF-7858" target="_blank">MPERF-7858</a>, <a href="https://jira.corp.magento.com/browse/MPERF-7846" target="_blank">MPERF-7846</a> --> Fixed several potential issues indicated by static code scans.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7707" target="_blank">MPERF-7707</a>. --> Resolved a potential man-in-the-middle vulnerability.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7649" target="_blank">MPERF-7649</a>.  -->Resolved a potential PHP security vulnerability.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8572" target="_blank">MPERF-8572</a>. --> An administrative user is no longer able to create a potential security vulnerability that used the block cache.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8363" target="_blank">MPERF-8363</a>. --> Resolved a potential <a href="https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)" target="_blank">cross-site request forgery (CSRF)</a> vulnerability involving the wishlist.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/APPSEC-1484" target="_blank">APPSEC-1484</a>.  -->Resolved a potential remote code excecution exploit.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/APPSEC-1517" target="_blank">APPSEC-1517</a>. --> It is no longer possible to  log in to a store as an existing customer using only an e-mail address.</li>




</ul>


<h4 id="ee114-1430security-pwd">Password enhancements</h4>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7728" target="_blank">MPERF-7728</a> --> A user can reset a password only after receiving an e-mail. In addition, we introduced the following configuration settings:
	<ul><li>Limit the number of forgotten password requests from one IP address to five times per hour.</li>
		<li>Limit the number of forgotten password requests from one e-mail address to five times per 24 hours.</li>
		<li>Limit the number of forgotten password requests to no more than once ever 10 minutes per e-mail address.</li></ul>
</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7609" target="_blank">MPERF-7609</a> --> The forgot password link expires after the first use or two hours (by default).</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7588" target="_blank">MPERF-7588</a>, <a href="https://jira.corp.magento.com/browse/MPERF-7982" target="_blank">MPERF-7982</a> --> When a user changes their e-mail address, they are required to provide their password and to acknowledge the change from the previous address.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8039" target="_blank">MPERF-8039</a> --> We now ignore leading and trailing spaces in a user's password.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6831" target="_blank">MPERF-6831</a> --> The new customer e-mail now includes the customer's password.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5029" target="_blank">MPERF-5029</a> --> Resetting a password using a password recovery e-mail succeeds.</li>


</ul>


	

</ul>




</ul>

<h3 id="ee114-1430security-upgrade">Check for <code>.swf</code> Files After Upgrade</h3>
<p>If you upgraded to Magento Commerce 1.14.3 after applying the <a href="https://magento.com/security/patches/supee-8788" target="_blank">SUPEE-8788 patch</a>, make sure the following files have been deleted:</p>

<pre>skin/adminhtml/default/default/media/flex.swf
skin/adminhtml/default/default/media/uploader.swf
skin/adminhtml/default/default/media/uploaderSingle.swf</pre>

<p>If the files are present, delete them to avoid a potential security exploit. As of Magento Commerce 1.14.0.0, we no longer distribute <code>.swf</code> files with the Magento software.</p>

<h3 id="ee114-1430back">Backward-Incompatible Changes</h3>
<p>The following backward-incompatible changes were made in this release:</p>
<p><code>Mage_Adminhtml_Block_Cms_Wysiwyg_Images_Content_Uploader</code>: Parent class was removed.</p>
<p><code>Mage_Uploader_Model_Config_Abstract</code>: Overrides the magic method <code>__call</code> and its behavior can be inconsistent. 例如: </p>

<pre>->setData('underscore_key', 1)
->getUnderscoreKey() //null</pre>


<h3 id="ee114-1430fixes">Fixes</h3>
<p>The following sections discuss other fixes in this release:</p>

<ul><li><a href="#ee114-1430tax">Tax Calculation Fixes</a></li>
	<li><a href="#ee114-1430fixes-cart">Shopping cart and checkout fixes</a></li>
	<li><a href="#ee114-1430fixes-cat">Catalog fixes</a></li>
	<li><a href="#ee114-1430fixes-price">Price rule fixes</a></li>
	<li><a href="#ee114-1430fixes-vm">Visual Merchandiser fixes</a></li>
	<li><a href="#ee114-1430fixes-swatch">Configurable swatches fixes</a></li>
	<li><a href="#ee114-1430fixes-import">Import/export fixes</a></li>
	<li><a href="#ee114-1430fixes-index">Indexer fixes</a></li>
	<li><a href="#ee114-1430fixes-other">Other fixes</a></li>
</ul>

<h4 id="ee114-1430tax">Tax Calculation Fixes</h4>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7035" target="_blank">MPERF-7035</a> --> The subtotal including tax on an invoice is calculated correctly. </li>


</ul>

<h4 id="ee114-1430fixes-cart">Shopping cart and checkout fixes</h4>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7685" target="_blank">MPERF-7685</a> --> One product displays one time in a cart even if the product was added once as a guest and another time as a logged-in user. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7634" target="_blank">MPERF-7634</a> --> Bundled products now display properly in the mini cart as well as the shopping cart. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8032" target="_blank">MPERF-8032</a> --> Moving a configurable product to a shopping cart in the Admin Panel functions normally. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7770" target="_blank">MPERF-7770</a> --> Shipping discount coupons are now based correctly on a customer's shipping address. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7426" target="_blank">MPERF-7426</a> --> First Class Mail letter now displays as a shipping option in the shopping cart. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7003" target="_blank">MPERF-7003</a> --> You can now pay for a product using both store credit and reward points. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6877" target="_blank">MPERF-6877</a> --> An exception no longer displays when a customer uses a gift card in an invalid transaction (such as an incorrect payment card number). </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5976" target="_blank">MPERF-5976</a> --> We added validation so a special price must be less than the actual price. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6909" target="_blank">MPERF-6909</a>  -->Exceptions no longer display when a customer checks out. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8844" target="_blank">MPERF-8844</a> --> Fixed a programming issue that prevented serializing and unserializing values in the shopping cart. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7403" target="_blank">MPERF-7403</a> --> Magento recovers from payment processor unavailability properly; the customer is charged and the item is shipped. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6985" target="_blank">MPERF-6985</a> --> You can no longer order an empty product; that is, a product with no options. </li>




</ul>

<h4 id="ee114-1430fixes-cat">Catalog fixes</h4>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7283" target="_blank">MPERF-7283</a> --> A configurable product with decimal quantity less 1 now displays the proper quantity in the catalog. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6530" target="_blank">MPERF-6530</a>  -->Configurable products are now sorted by attribute, not by product ID. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7962" target="_blank">MPERF-7962</a> --> Errors no longer display when you use <code>Mage_Catalog_Block_Product_List</code> on a product detail page. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7998" target="_blank">MPERF-7998</a> --> Removed the undefined variable <code>where</code> from <code>app/code/core/Mage/CatalogSearch/Model/Resource/Fulltext.php</code>. </li>




</ul>

<h4 id="ee114-1430fixes-price">Price rule fixes</h4>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7314" target="_blank">MPERF-7314</a> --> A catalog price rule that targets a bundled product by percentage calculates the price properly. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6346" target="_blank">MPERF-6346</a> --> A shopping cart price rule that includes tax now calculates properly. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6903" target="_blank">MPERF-6903</a> --> With the flat product catalog enabled, a catalog price rule with multi-select attributes works properly. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5246" target="_blank">MPERF-5246</a> --> Errors no longer display when two users add a product at the same time. Magento thanks Babenko eCommerce for contributing this fix. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6980" target="_blank">MPERF-6980</a> --> You can now add configurable products to the shopping cart after configuring a shopping cart rule. </li>


</ul>
<h4 id="ee114-1430fixes-vm">Visual Merchandiser fixes</h4>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8541" target="_blank">MPERF-8541</a> --> We bundled the following fixes in a patch:

	<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6193" target="_blank">MPERF-6193</a> --> The value of <strong>Attribute</strong> in the Smart Category section displays the entire category name. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7719" target="_blank">MPERF-7719</a> --> We reduced the frequency of rebuilding the Visual Merchandiser index to improve efficiency and performance. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8168" target="_blank">MPERF-8168</a> --> Duplicate products no longer display when you choose to hide not-visible products. </li>
		<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7577" target="_blank">MPERF-7577</a> --> Reapplied patches for various functions like indexing. </li>

</ul>
</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6218" target="_blank">MPERF-6218</a> --> Improved the display of the out of items message. </li>


</ul>

<h4 id="ee114-1430fixes-swatch">Configurable swatches fixes</h4>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7036" target="_blank">MPERF-7036</a> --> Fixed a memory leak in the configurable swatches module. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7631" target="_blank">MPERF-7631</a>  -->Configurable swatches for out-of-stock products now display consistently in layered navigation, the category view page, and the product view page. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7066" target="_blank">MPERF-7066</a> --> Configurable swatches work properly even if there is no image (before the fix, a JavaScript error was thrown). </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8763" target="_blank">MPERF-8763</a> --> Resolved performance issues. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7066" target="_blank">MPERF-7066</a> --> Swatch images for configurable products display properly. </li>




</ul>


<h4 id="ee114-1430fixes-import">Import/export fixes</h4>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2074" target="_blank">MPERF-2074</a>  -->We bundled the following fixes in a patch:
	<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2074" target="_blank">MPERF-2074</a>  -->Exporting a large number of products no longer results in an out-of-memory error. </li>
		<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3579" target="_blank">MPERF-3579</a> --> You can import into multiple stores if some stores are set to be replaced. </li>
		<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3528" target="_blank">MPERF-3528</a> --> Re-importing customers that have a multi-select attribute preserves the attribute. </li>
		<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3689" target="_blank">MPERF-3689</a> --> File uploads are processed properly. </li>
		<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7675" target="_blank">MPERF-7675</a> --> Fixed broken help links in the Magento Admin Panel. </li>
	
</ul>
</li>


	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4068" target="_blank">MPERF-4068</a> --> Importing products no longer consumes an excessive amount of memory. </li>
	
	
	
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5891" target="_blank">MPERF-5891</a> --> Coupon reports exported as <code>.csv</code> now display the correct totals. </li>



</ul>

<h4 id="ee114-1430fixes-index">Indexer fixes</h4>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5426" target="_blank">MPERF-5426</a> --> With flat category tables enabled, reindexing no longer removes the category class tag. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7028" target="_blank">MPERF-7028</a> --> Resolved errors with the Product Flat Index not completely indexing a large number of changes. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5198" target="_blank">MPERF-5198</a> --> All indexes now reindex when set to update when scheduled. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5336" target="_blank">MPERF-5336</a> --> Improved performance of the category indexers. Magento thanks Vaimo for contributing this fix.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2141" target="_blank">MPERF-2141</a>  -->Categories saved with a <code>/</code> character as the suffix display properly.</li>


	</ul>

<h4 id="ee114-1430fixes-other">Other fixes</h4>
<ul>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8575" target="_blank">MPERF-8575</a> --> Applied United States Postal Service API changes for <a href="https://www.usps.com/business/web-tools-apis/documentation-updates.htm" target="_blank">January 17, 2016</a>. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7785" target="_blank">MPERF-7785</a> --> Default variable values now save normally. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7424" target="_blank">MPERF-7424</a> --> The WYSIWYG editor handles XHTML tags like <code>cellpadding</code>和<code>cellspacing</code> properly. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7362" target="_blank">MPERF-7362</a> --> The configuration setting <strong>Allow HTML Tags on Frontend</strong> is honored. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7349" target="_blank">MPERF-7349</a> --> Orders created using the Magento Admin now display on the Orders and Returns page on the storefront. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7348" target="_blank">MPERF-7348</a> --> The option to merge Cascading Stylesheets (CSS) and JavaScript now works properly with a responsive web design (RWD) theme. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7324" target="_blank">MPERF-7324</a> --> On a mobile device when the Magento storefront uses an RWD theme, the Filter bar displays one time only. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7320" target="_blank">MPERF-7320</a> --> The Magento Connect Manager downloader's <code>.htaccess</code> file is no longer overwritten when the downloader component is updated. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7258" target="_blank">MPERF-7258</a> --> The configuration cache is no longer corrupted under heavy load. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7062" target="_blank">MPERF-7062</a> --> Order update e-mails are sent only once. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7049" target="_blank">MPERF-7049</a> --> A SOAP API call to <code>/api/soap/?wsdl</code> returns normally. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6475" target="_blank">MPERF-6475</a> --> A value that contains special characters is handled without errors by the SOAP API. </li>
	
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7000" target="_blank">MPERF-7000</a> --> Fixed the untranslatable <code>base/default/template/sales/guest/form.phtml</code> template. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6910" target="_blank">MPERF-6910</a> --> Magento now stores two-digit birth years properly (for example, <code>80</code> is stored as <code>1980</code>). </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6891" target="_blank">MPERF-6891</a> --> HTTP 200 (OK) status codes are returned for pages after a session expires. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6802" target="_blank">MPERF-6802</a> --> You can view a disabled product without errors if compilation is enabled. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6387" target="_blank">MPERF-6387</a> --> A Value Added Tax (VAT) ID now validates properly. If the customer specifies an invalid ID, the customer is notified they will be charged VAT tax. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5492" target="_blank">MPERF-5492</a> --> Listing shipments no longer displays an exception. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5162" target="_blank">MPERF-5162</a> --> You can filter associated products for a group product without errors. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5155" target="_blank">MPERF-5155</a> --> When you manage product attributes, selecting an action from <strong>Actions</strong> works properly. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3281" target="_blank">MPERF-3281</a> --> You can now add a configurable product by SKU to an order using the Admin Panel. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2615" target="_blank">MPERF-2615</a> --> You can now save a product's weight attribute. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-1808" target="_blank">MPERF-1808</a> --> You can now save changes to a CMS page hierarchy when hierarchy metadata is disabled. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5798" target="_blank">MPERF-5798</a>  -->You can now save a banner after upgrading. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7047" target="_blank">MPERF-7047</a> --> Using a Portable Network Graphics (<code>.png</code>) image on a CMS page no longer results in a <code>HEADERS_ALREADY_SENT</code> message to be logged. </li>
	<li>Fixed an exception related to an unknown database table. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7059" target="_blank">MPERF-7059</a> --> Fixed an issue with JavaScript merging. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7053" target="_blank">MPERF-7053</a>  -->You can now print 10 or more shipping labels without issues. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7500" target="_blank">MPERF-7500</a> --> A PHP notice no longer occurs when you log the Magento Admin Panel IP address in the event log. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7068" target="_blank">MPERF-7068</a>  -->A SQL error no longer displays when you create a new floating point product attribute programmatically. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6881" target="_blank">MPERF-6881</a> --> Added a missing image to the codebase. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7063" target="_blank">MPERF-7063</a> --> The expression <code>Mage::getModel('core/variable')->addValuesToResult()</code> returning a collection with column <code>plain_value</code>和<code>html_value</code> now returns a collection with columns <code>plain_value</code>和<code>html_value</code>. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-6909" target="_blank">MPERF-6909</a> --> Payment no longer results in the exception <code>ERR (3): Notice: Undefined offset: 1 in app/code/core/Mage/Sales/Model/Order.php on line 1258</code>. </li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8069" target="_blank">MPERF-8069</a>  -->The correct telephone number displays in transactional e-mails. We changed the variable <code>phone</code> to <code>store_phone</code>. Magento thanks Classy Llama Studios for contributing this fix.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7918" target="_blank">MPERF-7918</a> --> The Google sitemap now lists store URLs properly.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8759" target="_blank">MPERF-8759</a> --> Implemented search query caching, which speeds up search results.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-8592" target="_blank">MPERF-8592</a> --> After a customer submits an order, the following error should not display: <code>SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'ECO0000148' for key 'UNQ_SALES_FLAT_ORDER_INCREMENT_ID'</code>.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5460" target="_blank">MPERF-5460</a> --> With flat category enabled, you no longer see errors due to an undefined method call.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5453" target="_blank">MPERF-5453</a> --> Case-sensitive variations of URL rewrites work as expected.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3718" target="_blank">MPERF-3718</a> --> Resolved a JavaScript syntax error in <code>bundle.js</code>.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7305" target="_blank">MPERF-7305</a>  -->The cron-related error <code>Warning: shell_exec() has been disabled for security reasons...</code> has been resolved. Magento thanks Stefan Hagspiel for reporting this issue.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7095" target="_blank">MPERF-7095</a> --> cron no longer runs multiple times unnecessarily.</li>
	<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-7817" target="_blank">MPERF-7817</a> --> Cached static blocks now display properly.</li>

</ul>

<h2 id="ee114-11420">Magento Commerce 1.14.2.0 Release Notes</h2>
<p>Magento Commerce 1.14.2.0 Release Notes are in the <a href="http://docs.magento.com/m1/ee/user_guide/magento/release-notes-ee-1.14.2.html" target="_blank">User Guide</a>.</p>

<h2 id="ee114-11410">Magento Commerce 1.14.1.0 Release Notes</h2>
<p>Magento Commerce 1.14.1.0 Release Notes are in the <a href="http://docs.magento.com/m1/ee/user_guide/magento/release-notes-ee-1.14.1.html" target="_blank">User Guide</a>.</p>

<h2 id="ee114-11401">Magento Commerce 1.14.0.1 Release Notes</h2>
<p>Magento Commerce 1.14.0.1 resolves the following issues:</p>
<ul><li><!-- https://jira.corp.magento.com/browse/MPERF-5270 -->Customers can no longer apply a coupon from an inactive shopping cart price rule to a purchase.</li>
<li>Customers using a smartphone or other small viewport can expand subcategories in the web store that uses the new responsive theme.</li></ul>

<h2 id="ee114-patches">Recent Patches</h2>
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-note.png" alt="note" align="left" width="40"><span><strong>注意</strong>: The patches discussed in this section are built in to Commerce 1.14.1; you need to get them only if you're running an earlier Commerce version.</div>

<p>We'd like to draw your attention to several new patches that were recently posted to the Partner Portal and Support Center. These patches deliver important improvements, such as enabling several concurrent administrators to work with the product catalog, and to make it easier to install community-created translation packages.</p>
<p>Details about the patches follow. To install these patches, see <a href="#ee114-patches-how-to-get">How to Get Patches For Magento Commerce</a>.</p>
<ul><li><a href="#ee114-patches-connect-general">General Magento Connect Patches</a></li>
<li><a href="#ee114-patches-soap">Magento Install Page Displays After SOAP v2 Index Page Refresh</a></li>
<li><a href="#ee114-patches-multi-admins">Multiple Simultaneous Magento Administrators</a></li>
<!-- <li><a href="#ee114-patches-solr-index">Solr Search Results and Indexing</a></li>
 --><li><a href="#ee114-patches-how-to-get">How to Get Patches For Magento Commerce</a></li> 
</ul>

<h3 id="ee114-patches-connect-general">General Magento Connect Patches</h3>
<p><em>Patch name</em>: PATCH_SUPEE-3941_EE_1.14.0.1_v1-2014-08-12-12-10-06.sh</p>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4558" target="_blank">MPERF-4558</a>, <a href="https://jira.corp.magento.com/browse/APPSTORE-4590" target="_blank">APPSTORE-4590</a> -->When you install a community-created translation package, the translation provided by the package overwrites any existing translations for the same items. This enables you to more easily install packages with translations. </li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4558" target="_blank">MPERF-4558</a>, <a href="https://jira.corp.magento.com/browse/APPSTORE-4589" target="_blank">APPSTORE-4589</a> -->To improve security, Magento Connect now uses HTTPS by default to download extensions, rather than FTP. </li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4558" target="_blank">MPERF-4558</a>, <a href="https://jira.corp.magento.com/browse/APPSTORE-4557" target="_blank">APPSTORE-4557</a> -->Extension developers can now create an extensions with a dash character in the name. Merchants can install those extensions without issues.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4558" target="_blank">MPERF-4558</a>, <a href="https://jira.corp.magento.com/browse/APPSTORE-4575" target="_blank">APPSTORE-4575</a> -->Magento administrators who attempt to install an extension with insufficient file system privileges are now informed. Typically, the Magento Admin Panel runs as the web server user. If this user has insufficient privileges to the <em>your Magento install dir</em><code>/app/code/community</code> directory structure, the Magento administrator sees an error message in the Magento Connect Manager.<br />
To set file system permissions appropriately, see <a href="{{ site.m1xgdeurl }}install/installer-privileges_after.html#extensions" target="_blank">After You 安装Magento: Recommended File System Ownership and Privileges</a>.</li></ul>

<h3 id="ee114-patches-soap">Magento Install Page Displays After SOAP v2 Index Page Refresh</h3>
<p><em>Patch name</em>: PATCH_SUPEE-3762_EE_1.14.0.1_v1.sh. <!-- <a href="https://jira.corp.magento.com/browse/SUPEE-3762" target="_blank">SUPEE-3762</a> -->Refreshing the SOAP v2 index page (<code>http://<em>your-magento-host-name</em>/index.php/api/v2_soap/index/</code>) results in all administrators and customers viewing the Magento installation page.</p>

<h3 id="ee114-patches-multi-admins">Multiple Simultaneous Magento Administrators</h3>
<p><em>Patch name</em>: PATCH_SUPEE-3819_EE_1.14.0.1_v1.sh. <!-- <a href="https://jira.corp.magento.com/browse/SUPEE-3819" target="_blank">SUPEE-3819</a> -->Multiple Magento administrators can simultaneously add new products; or edit descriptions, edit prices, or edit stock quantities of existing products without causing deadlocks, key violations, or critical data errors. Together with applying the patch, you must set all indexers to Update when scheduled as follows:</p>
<ol><li>Log in to the Magento Admin Panel as an administrator.</li>
<li>Click <strong>System</strong> > <strong>Configuration</strong>.</li>
<li>In the left navigation bar, from the ADVANCED group, click <strong>Index Management</strong>.</li>
<li>Expand <strong>Indexing Options</strong>.</li>
<li>From each list, click <strong>Update when scheduled</strong>.</li>
<li>Click <strong>Save Config</strong> in the upper right corner of the page.</li></ol>

<!-- <h3 id="ee114-patches-solr-index">Solr Search Results and Indexing</h3> -->
<!-- <p><em>Patch name</em>: PATCH_SUPEE-3630_EE_1.13.x-1.14.x_v1.sh.  --><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5050" target="_blank">MPERF-5050</a>, <a href="https://jira.corp.magento.com/browse/SUPEE-3630" target="_blank">SUPEE-3630</a> --><!-- After applying this patch, your search engine returns search results to users on the web store while reindexing is underway. We recommend you install this patch if you're using the Solr search engine. <em>This patch can result in slower performance if you're using the default MySQL Full Text search engine</em>.</p> -->
<!-- <p>To get this patch, <a href="https://www.magentocommerce.com/products/customer/account/login/" target="_blank">contact Magento Support</a>.</p> -->

<h3 id="ee114-patches-how-to-get">How to Get Patches For Magento Commerce</h3>
<p>This section discusses how to get patches referenced in these Release Notes. Magento has other patches available from the Commerce support portal and the <a href="https://partners.magento.com" target="_blank">partner portal</a>; you can use the following instructions to install any of those patches as well.</p>
<p>To get patches for Magento Commerce:</p>
<ol><li>Log in to <a href="http://www.magentocommerce.com" target="_blank">www.magentocommerce.com</a>.</li>
<li>In the left pane, click <strong>Downloads</strong>.</li>
<li>In the right pane, click <strong>Magento Commerce</strong>.</li>
<li>Follow the prompts on your screen to download a patch for your version of EE.</li>
<li>Apply the patch as discussed in <a href="{{ site.m1xgdeurl }}other/ht_install-patches.html" target="_blank">How to Apply and Revert Magento Patches</a>.</li></ol>

<h2 id="ee114-11400">Magento Commerce 1.14.0.0 Release Notes</h2>
<p>See the following sections for information about changes in this release:</p>
<ul><li><a href="#ee114-11400-highlights">Highlights</a></li>
<li><a href="#ee114-1400security">Security Enhancements</a></li>
<li><a href="#ee114-11400-changes">Changes</a></li>
<li><a href="#ee114-1400tax">Tax Calculation Fixes</a></li>
<li><a href="#ee114-1400fixes">Fixes</a></li>
</ul> 

<h3 id="ee114-11400-highlights">Highlights</h3>
<p>This section lists the key new features in Magento Commerce 1.14. For more information about these new features, see the <a href="http://www.magentocommerce.com/resources/magento-user-guide" target="_blank">Magento User Guide</a>.</p>
<ul><li>The default theme in Magento Commerce 1.14 uses <a href="https://en.wikipedia.org/wiki/Responsive_web_design" target="_blank">Responsive Web Design</a> principles to provide a better experience for users of mobile devices in particular. Benefits include:
<ul><li>You can get a tablet and smart phone friendly responsive site in about half the time as before, speeding time to market and freeing up resources for other projects.</li>
<li>Your responsive site makes you better able to participate in the fast growing mobile commerce space, gives you the ability to more easily adapt to new opportunities, and is less expensive to maintain.  A responsive site also offers potential search engine optimization (SEO) benefits because it uses Google's preferred approach to mobile-optimizing sites.</li></ul>
</li>
<li>Magento Commerce 1.14 now supports Solr versions up to 3.6.2 natively (that is, without a patch). Catalog indexing happens efficiently and automatically in the background, with no manual intervention required, resulting in better administrative performance. <br />
For more information about using Solr with Magento Commerce, see the <a href="http://www.magentocommerce.com/resources/magento-user-guide" target="_blank">Magento User Guide</a>.<br />
<strong>注意</strong>: If you're using the Solr search engine with Commerce versions 1.13.1 or earlier, you must perform an additional step during upgrade due to the fact that the Solr schema changes in Commerce 1.14. You must copy two files to your Solr server&mdash;<code>schema.xml</code>和<code>solrconfig.xml</code>. For details, see <a href="{{ site.m1xgdeurl }}install/installing_upgrade_details.html#upgrade-manual-solr" target="_blank">the section on upgrading Solr in the Magento upgrade guide</a>.</li>
<li>Cross-border trade: (Also referred to as <em>pricing consistency</em>.) We support European Union (EU) merchants operating across regions and geographies who want to show their customers a single price. Pricing is clean and uncluttered regardless of tax structures and rates that vary from country to country.<br />
To enable cross-border trade in the Admin Panel, click <strong>System</strong> > <strong>Configuration</strong> > SALES > <strong>Tax</strong> > <strong>Calculation Settings</strong>, option <strong>Enable Cross Border Trade</strong>.</li>
<li>Supports <a href="http://www.php.net/manual/en/migration54.changes.php" target="_blank">PHP 5.4</a>. For more information, see <a href="http://php.net/ChangeLog-5.php#5.4.0" target="blank">the PHP changelog</a>.</li>
<li>The Zend Framework has been upgraded to <a href="http://framework.zend.com/changelog/1.12.3/" target="_blank">version 1.12.3</a></li>
<li>Checkout improvements:
<ul><li>You can capture up to 18% more sales  by providing customers access to financing using the Bill Me Later service at no additional cost to you. </li>
<li>You can offer your customers a smoother, more streamlined PayPal Express Checkout experience, which tries alternative payment options when a customer's credit card is rejected</li>
<li>Improve the PayPal Express checkout experience by eliminating the following steps in the checkout process:
<ul class="level3"><li>The order review page can be enabled or disabled</li>
<li>Eliminate the necessity of clicking <strong>Update Order</strong> before <strong>Place Order</strong></li></ul>
</li>
</li>
</ul>
<p>(<em>Conversion</em> means helping customers stay interested and complete their purchases.)</p>
</ul>

<h3 id="ee114-1400security">Security Enhancements</h3>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4809" target="_blank">MPERF-4809</a> -->Addressed a potential cross-site scripting (XSS) vulnerability while creating configurable product variants.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3723" target="_blank">MPERF-3723</a> -->Addressed a potential security issue that could result in displaying information about a different order to a customer.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3114" target="_blank">MPERF-3114</a> -->Users can no longer change the currency if the payment method PayPal Website Payments Standard is used.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3076" target="_blank">MPERF-3076</a> -->Removed an <code>.swf</code> file from the Magento distribution because of security issues.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2119" target="_blank">MPERF-2119</a> -->Improved file system security.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2498" target="_blank">MPERF-2498</a> -->Enhanced the security of action URLs, such as billing agreements.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-1899" target="_blank">MPERF-1899</a> -->Addressed a potential session fixation vulnerability during checkout.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2807" target="_blank">MPERF-2807</a> -->Improved the security of the Magento randomness function.</li>
</ul>

<h3 id="ee114-11400-changes">Changes</h3>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4632" target="_blank">MPERF-4632</a> -->A default setting for configurable and bundled products has changed. When you create a configurable or bundled product in the Admin Panel, click <strong>Manage</strong> > <strong>Products</strong>. Create a new configurable or bundled product and click the <strong>Design</strong> tab. The default option for <strong>Display Product Options In</strong> has changed to <strong>Product Info Column</strong>.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4870" target="_blank">MPERF-4870</a> -->The Google Websites Optimizer has been disabled because it has been deprecated by Google. (In earlier Commerce versions, this option was available in the Admin Panel at <strong>System</strong> > <strong>Configuration</strong> > SALES > <strong>Google API</strong> > <strong>Google Website Optimizer</strong>).</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2563" target="_blank">MPERF-2563</a> -->Two new options to prevent <a href="http://en.wikipedia.org/wiki/Clickjacking" target="_blank">"clickjacking"</a> if you run Magento in a <code>frame</code>或<code>iframe</code>:
<ul><li>Enable frames only in the same domain.</li>
<li>Enable frames.</li>
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-note.png" alt="note" align="left" width="40"><span><strong>注意</strong>: For security reasons, Magento strongly recommends against running the Magento software in a frame.</div>

<p>The options are available in the Admin Panel at <strong>System</strong> > <strong>Configuration</strong> > ADVANCED > <strong>Admin</strong> > <strong>Security</strong> and are named <strong>Allow Magento Backend to run in frame</strong>和<strong> Allow Magento Frontend to run in frame</strong>.</p>
<p>Enabling the option causes the <a href="https://developer.mozilla.org/en-US/docs/HTTP/X-Frame-Options" target="_blank"><code>X-Frame-Options</code></a> request header to be sent.</p></ul>
</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4970" target="_blank">MPERF-4970</a> -->FedEx changed their endpoints for sandbox and production to the following:
<ul><li>Production: https://ws.fedex.com/web-services</li>
<li>Sandbox: https://wsbeta.fedex.com/web-services</li></ul>
<p>Because of these changes, Magento cannot retrieve shipping rate information or print shipping labels for FedEx unless this fix is applied.</p>
</li>
<!-- <li><a href="https://jira.corp.magento.com/browse/MPERF-3769" target="_blank">MPERF-3769</a> Added address validation, which enables users to select from multiple matching addresses. 例如， if a user enters a partial address or a common street name, they might be presented with matching addresses from which to choose.</li>
 -->
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4620" target="_blank">MPERF-4620</a>.  -->Magento Commerce 1.14 includes a fix that prevented some Discover credit cards from validating properly. The issue was that certain Discover credit card number ranges were not recognized as being valid. As a result of the fix, all Discover cards should validate properly.</p>
<div class="msg-box important"><img src="{{ site.baseurl }}/common/images/m1x/icon-note.png" alt="note" align="left" width="40"><span><strong>注意</strong>: This is <em>not</em> a security threat. No data has been compromised or misused. It affects only the ability to validate certain credit card number ranges as valid Discover card numbers.</div></li>
<li>If you use the Solr search engine, you no longer need to manually reindex the Catalog Search Index (except after you upgrade to EE 1.14 from an earlier version).</li>
<li>The default values for two configuration options changed. Both options can be found in the Admin Panel under <strong>System</strong> > <strong>Configuration</strong> > CATALOG > <strong>Catalog</strong> > <strong>Frontend</strong>. The new default values follow:
<ul><li><strong>Products per Page on Grid Allowed Values</strong> is now <strong>12, 24, 36</strong>.</li>
<li><strong>Products per Page on Grid Default Value</strong> is now <strong>12</strong>.</li></ul>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5142" target="_blank">MPERF-5142</a>.  -->On the New Rule page for shopping cart price rules (<strong>Rule Information</strong> tab page), explanatory text <strong>Usage limit enforced for logged in customers only</strong> was added to the <strong>Uses per customer field</strong>. This is to avoid confusion encountered by some Magento merchants.</li>
<li>Changes to PayPal Express checkout:
<ul><li>Changes to both <strong>Proceed to Checkout</strong> and to <strong>Pay With PayPal</strong>:
<ul class="level3"><li>Customers cannot edit their billing address on the PayPal site&mdash;in fact, the billing address does not display on the PayPal site.</li>
<li>Magento Commerce uses the customer's PayPal address information, not the address information stored in Magento Commerce. The customer does not need to enter Magento Open Source or Commerce address information.</li>
<li>When the customer is redirected to the PayPal site, they can click <strong>Change</strong> next to their payment method to change it.</li>
<p>The Magento administrator can set billing address information in the Admin Panel as follows: <strong>System</strong> > <strong>Configuration</strong> > SALES > <strong>Payment Methods</strong>. For any payment method that includes Express Checkout, in Basic Settings, set the value of the <strong> Require Customer's Billing Address</strong> list.</p>
</ul>
</li>
</ul>
<ul><li>Changes to <strong>Pay With PayPal</strong> only:
<ul class="level3"><li>If the Magento administrator does not require the customer's billing address, the customer's billing address is set to the customer's PayPal <em>shipping</em> address.</li>
<li>If the Magento requires the customer's billing address, the customer's billing address is set to the customer's PayPal <em>billing</em> address.</li>
<li>On the PayPal site, the customer can click <strong>Change</strong> next to their shipping address to change it. The customer can choose any shipping address configured with PayPal.</li>
<li>Because the customer's configured address in Magento is not used, the customer's shipping address stored in PayPal is never changed.</li></ul>
</li></ul>
<ul><li>Changes to <strong>Proceed to Checkout</strong> only:
<ul class="level3"><li>No <strong>Change</strong> link displays next to a customer's shipping address on the PayPal site.</li>
<li>In the event of a shipping address mismatch between Magento and PayPal, the following message displays when the customer attempts to pay using PayPal:<br />
<pre>The address you entered on <em>store-name</em> is different than your PayPal preferred shipping address. 
返回到 <em>store-name</em> if you'd like to change the shipping address</pre>
The user can select the <strong>Use as preferred shipping address</strong> check box to instruct PayPal to change their shipping address.</li>
</li></ul>
</li></ul>
</li>

</ul>

<h3 id="ee114-1400tax">Tax Calculation Fixes</h3>
<ul><!-- <li><a href="https://jira.corp.magento.com/browse/MPERF-4818" target="_blank">MPERF-4818</a>. With cross-border trading enabled for a subset of websites, an order placed by an administrative user when product prices are calculated including taxes.<br /> 
To enable cross-border trading: <strong>System</strong> > <strong>Configuration</strong> > SALES > <strong>Tax</strong> > Calculation Settings</strong>.<br />
To enable product price display including tax: <strong>System</strong> > <strong>Configuration</strong> > SALES > <strong>Tax</strong> > <strong>Price Display Settings</strong>.</li> -->
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4832" target="_blank">MPERF-4832</a> -->Fixed price and dynamic price bundled products where the price is configured to include tax display prices correctly regardless of tax settings. (例如， customer's default tax rate is different from the origin tax rate.) </li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4764" target="_blank">MPERF-4764</a> -->Resolved a one-cent rounding issue when Fixed Product Tax (FPT) is enabled and the option <strong>Apply Discount to FPT</strong> is set to <strong>Yes</strong>. (These options are available in the Admin Panel by going to <strong>System</strong> > <strong>Configuration</strong> > SALES > <strong>Tax</strong> > <strong>Fixed Product Taxes</strong>.)</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4619" target="_blank">MPERF-4619</a> -->Resolved issues with calculating the credit memo amount when FPT is discounted and the customer purchases more than one item.</li>
</ul>

<h3 id="ee114-1400fixes">Fixes</h3>
<!-- Support, a list of all regressions fixed in this release can be found here: https://jira.corp.magento.com/secure/Dashboard.jspa?selectPageId=14815 -->
<p>Fixes in this release can be divided into the following categories:</p>
<ul><li><a href="#ee114-1400fixes-webstore">Web Store and Shopping Cart Fixes</a></li>
<li><a href="#ee114-1400fixes-price-rules">Promotional Price Rule Fixes</a></li>
<li><a href="#ee114-1400fixes-adminpanel">Administrative Ordering, Invoicing, Credit Memo Fixes</a></li>
<li><a href="#ee114-1400fixes-importexport">Import Fixes</a></li>
<li><a href="#ee114-1400fixes-payment">Payment Method Fixes</a></li>
<li><a href="#ee114-1400solr">Solr Search Engine Fixes</a></li>
<li><a href="#ee114-1400fixes-other">Other Fixes</a></li></ul>

<h4 id="ee114-1400fixes-webstore">Web Store and Shopping Cart Fixes</h4>
<ul><li>With full page caching enabled:
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4735" target="_blank">MPERF-4735</a>, <a href="https://jira.corp.magento.com/browse/MPERF-4362" target="_blank">MPERF-4362</a> -->Customers can no longer see each other's wish list or previously viewed products.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4199" target="_blank">MPERF-4199</a> -->Related products set to not rotate display on the web store. (In other words, an administrator set <strong>System</strong> > <strong>Configuration</strong> > CATALOG > <strong>Catalog</strong> > <strong>Rule-Based Product Relations</strong>, option <strong>Rotation Mode for Products in Related Product List</strong> set to <strong>Do not rotate</strong>.)</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4885" target="_blank">MPERF-4885</a> -->The product ratings block refreshes on the storefront after a new rating has been approved.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4989" target="_blank">MPERF-4989</a> -->Tier pricing is calculated properly.</li>
</ul>
</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4042" target="_blank">MPERF-4042</a> -->Resolved a 404 (Not Found) error navigating from a product in one category to an upsell product in a different category.</li>

<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4836" target="_blank">MPERF-4836</a> -->A customer can update quantities of items in their mini shopping cart from their My Account page.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3138" target="_blank">MPERF-3138</a> -->The Minimum Advertised Price pop-up works properly in the web store. When the customer clicks <strong>Click for price</strong>, the price displays as expected.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4819" target="_blank">MPERF-4819</a> -->The "customer since" date is correct.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3767" target="_blank">MPERF-3767</a> -->Switching stores when viewing a product with store-scoped URL keys works as expected.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3928" target="_blank">MPERF-3928</a> -->Setting <strong>System</strong> > <strong>Configuration</strong> > CATALOG > <strong>Inventory</strong>, option <strong>Display Out of Stock Products</strong> to <strong>Yes</strong> no longer causes all products to appear as out of stock.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3280" target="_blank">MPERF-3280</a> -->Entering accented characters in the zip code field during checkout results in a validation error instead of an exception message.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3509" target="_blank">MPERF-3509</a> -->Gift card codes are sent only after an item is purchased.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-343" target="_blank">MPERF-343</a> -->A customer who attempts to log in as another customer with incorrect credentials is denied.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4753" target="_blank">MPERF-4753</a> -->Resolved issues with applying a 100% discount to an order.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3657" target="_blank">MPERF-3657</a> -->Customers are no longer redirected to the home page when they have permission to view a category.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-1360" target="_blank">MPERF-1360</a> -->Discount amount displays correctly for products with custom options.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5232" target="_blank">MPERF-5232</a> -->Issues with placing PayPal Payments Advanced or PayPal Payflow Link orders using IE9 have been resolved.</li>
</ul>

<h4 id="ee114-1400fixes-price-rules">Promotional Price Rule Fixes</h4>
<p>The following fixes relate to administering and using shopping cart price rules and catalog price rules:</p>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2535" target="_blank">MPERF-2535</a> -->Shopping cart price rules apply properly to grouped products.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3242" target="_blank">MPERF-3242</a> -->Two catalog price rules applied to the same product work properly.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3741" target="_blank">MPERF-3741</a> -->The setting <strong>Stop Further Rules Processing</strong> is honored.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4901" target="_blank">MPERF-4901</a> -->A user with read-only privileges in the Admin Panel cannot save changes to a price rule.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2614" target="_blank">MPERF-2614</a> -->Applying a shopping cart price rule does not display an exception.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2518" target="_blank">MPERF-2518</a> -->Coupon codes apply only to products eligible for the price rule.</li>
<!-- <li><a href="https://jira.corp.magento.com/browse/MPERF-3764" target="_blank">MPERF-3764</a> Corrected calculation issues when there are more than 1,000 catalog price rules.</li>
 -->
</ul>

<h4 id="ee114-1400fixes-adminpanel">Administrative Ordering, Invoicing, Credit Memo Fixes</h4>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2407" target="_blank">MPERF-2407</a> -->An administrative user with access to only one website from which a product was deleted no longer sees a stack trace when attempting to create an RMA for that product. In other words, after a customer placed an order for a product on Website1, an administrator with privileges to all websites removes the product. Later, when an administrator with access to only Website1 attempts to create an RMA for the deleted product, that administrator no longer sees an error message; instead, they see an expected <code>Access Denied</code> message.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4606" target="_blank">MPERF-4606</a> -->Resolved an issue with incorrectly calculating the amount of an invoice when some items were discounted by a shopping cart price rule.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4607" target="_blank">MPERF-4607</a> -->Credit memo amount is calculated correctly when processing a partial invoice with a discount.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4041" target="_blank">MPERF-4041</a> -->Making comments in a credit memo no longer returns items to stock. (Prerequisite: an administrator set <strong>System</strong> > <strong>Configuration</strong> > CATALOG > <strong>Inventory</strong> > <strong>Product Stock Options</strong>, option <strong>Automatically Return Credit Memo Item to Stock</strong> set to <strong>Yes</strong>.)</li>
 
</ul>

<h4 id="ee114-1400fixes-importexport">Import Fixes</h4>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3702" target="_blank">MPERF-3702</a> -->A product with a custom attribute set imports successfully.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-5505" target="_blank">MPERF-5505</a>  -->A fatal error caused by <code>Mage_ImportExport_Model_Scheduled_Operation</code> was fixed.<br>
Magento thanks Tim Bezhashvyly for contributing to this fix.</li>
</ul>

<h4 id="ee114-1400fixes-payment">Payment Method Fixes</h4>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3113" target="_blank">MPERF-3113</a> -->If guest checkout is disabled, a customer must log in to check out with PayPal Express.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4827" target="_blank">MPERF-4827</a> -->Eliminated errors in the logs when an administrator clicks <strong>System</strong> > <strong>Configuration</strong> > SALES > <strong>Payment Methods</strong>.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4894" target="_blank">MPERF-4894</a> -->You can now use New Zealand dollars as the base currency with the eWAY Direct payment bridge.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4813" target="_blank">MPERF-4813</a> -->Store credit is applied correctly when using Website Payments Pro Hosted Solution.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2729" target="_blank">MPERF-2729</a> -->If the merchant country is Germany (DE), disabled guest checkout for the express checkout method and PayPal Website Payments Standard.</li>
</ul>
 
<h4 id="ee114-1400solr">Solr Search Engine Fixes</h4>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4460" target="_blank">MPERF-4460</a> -->Eliminated a spurious error from the logs when Solr is enabled as the search engine.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4346" target="_blank">MPERF-4346</a> -->Solr sorts search results by score.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4197" target="_blank">MPERF-4197</a> -->A quick search by SKU works with the Solr search engine if the SKU contains hyphen characters.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3745" target="_blank">MPERF-3745</a> (<a href="https://jira.corp.magento.com/browse/SUPEE-1804" target="_blank">SUPEE-1804</a>) -->Solr search works properly if you set <code>allow_url_fopen = Off</code> in <code>php.ini</code>.</li>
<li><!-- (<a href="https://jira.corp.magento.com/browse/SUP-4880" target="_blank">SUP-4880</a>)  -->Using layered navigation filtering no longer returns the wrong results. (例如， filtering by brand works properly.)</li>
<li><!--( <a href="https://jira.corp.magento.com/browse/SUP-4901" target="_blank">SUP-4901</a>)  -->Resolved an issue where search results don't display correctly after a Magento upgrade.</li>
<li><!-- (<a href="https://jira.corp.magento.com/browse/SUP-5164" target="_blank">SUP-5164</a>)  -->Catalog navigation works properly.</li>
<li><!-- (<a href="https://jira.corp.magento.com/browse/MAGETWO-1417" target="_blank">MAGETWO-1417</a>)  -->Products display as expected in categories if the products have a Date attribute with the option <strong>Used for Sorting in Product Listing</strong> set to <strong>Yes</strong>. There are no exceptions in Magento logs after reindexing.</li>
<li><!-- (<a href="https://jira.corp.magento.com/browse/SUPEE-646" target="_blank">SUPEE-646</a>)  -->Corrected the sort order of products searched by SKU.</li>
<li><!-- (<a href="https://jira.corp.magento.com/browse/SUPEE-843" target="_blank">SUPEE-843</a>, <a href="https://jira.corp.magento.com/browse/SUPEE-1034" target="_blank">SUPEE-1034</a>)  -->Search results of products with names and/or SKUs that contains numbers, letters, and a hyphen character (-) are as expected.</li>
<li><!-- (<a href="https://jira.corp.magento.com/browse/SUPEE-1283" target="_blank">SUPEE-1283</a>)  -->Resolved issues with search results for products in a locale other than en_US with numeric SKUs.</li>
<li><!-- (<a href="https://jira.corp.magento.com/browse/SUPEE-954" target="_blank">SUPEE-954</a>)  -->Resolved issues with Solr not returning product search results.</li>
<li><!-- (<a href="https://jira.corp.magento.com/browse/SUPEE-1833" target="_blank">SUPEE-1833</a>)  -->Search results no longer include products that are either Disabled or Out of Stock.</li>


</ul>

<h4 id="ee114-1400fixes-other">Other Fixes</h4>
<ul><li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4808" target="_blank">MPERF-4808</a> -->Restored images on a customer's Reward Points page.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4815" target="_blank">MPERF-4815</a> -->Categories on the storefront now display with spaces between category names for cached and non-cached pages.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4792" target="_blank">MPERF-4792</a> -->A customer can now initiate a return from the storefront.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4749" target="_blank">MPERF-4749</a> -->An administrative user can subscribe to low stock RSS feeds without errors.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3273" target="_blank">MPERF-3273</a> -->Category URLs work as expected, regardless of the setting of <strong>Create Custom Redirect for old URL</strong> for the category's URL key.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4247" target="_blank">MPERF-4247</a> -->Setting <code>allow_url_fopen = Off</code> in <code>php.ini</code> has no effect on the CMS WYSIWYG editor.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4351" target="_blank">MPERF-4351</a> -->No fatal error displays when a role-restricted user previews a newsletter in the Admin Panel.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4266" target="_blank">MPERF-4266</a> -->Google Sitemap files now include the <code>.html</code> suffix for category and product URLs.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4267" target="_blank">MPERF-4267</a> -->Customers can use advanced search on your storefront if Magento EE is configured to use the default MySQL Fulltext search engine and the server uses MySQL 5.6.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3511" target="_blank">MPERF-3511</a> -->A role-restricted user can preview a newsletter in the Admin Panel to which the user has privileges.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2805" target="_blank">MPERF-2805</a> -->After synchronizing media files with the database, <code>media/customer/.htaccess</code> is present with the correct data. (Prerequisite: an administrator set <strong>System</strong> > <strong>Configuration</strong> > ADVANCED > <strong>System</strong> > <strong>Storage Configuration for Media</strong> set to <strong>数据库</strong>).</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3159" target="_blank">MPERF-3159</a> -->cron now restarts indexers if they previously failed to run.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2146" target="_blank">MPERF-2146</a> -->You can save changes to a category that has more than 1,000 products.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2492" target="_blank">MPERF-2492</a> -->Deactivating one of several banners no longer causes exceptions in <code>system.log</code>.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3025" target="_blank">MPERF-3025</a> --> Resolved issues with the WSDL cache.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2246" target="_blank">MPERF-2246</a> -->Improved the efficiency of product searches.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2413" target="_blank">MPERF-2413</a> -->Resolved issues with the full page cache crawler.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3652" target="_blank">MPERF-3652</a> -->Resolved issues with the DHL International shipping method.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-2221" target="_blank">MPERF-2221</a> -->Resolved 404 (Not Found) errors in layered navigation.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-4984" target="_blank">MPERF-4984</a> -->Resolved a SQL error when attempting to assign a bundled product to another website.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-3749" target="_blank">MPERF-3749</a> -->Rules-based product relations perform as expected after being saved.</li>
<li><!-- <a href="https://jira.corp.magento.com/browse/MPERF-1838" target="_blank">MPERF-1838</a> -->Resolved an issue with sending duplicate <code>Content-Type</code> headers when using <code>mod_fastcgi</code> with the Apache web server.</li>



</ul>


<h2 id="oss">Open Source Software Licensing Agreements</h2>
<p>Some versions of Magento Commerce use open source software licensing. Following are license agreements for that software.</p>
<p><strong>Touch punch</strong>: This code is dual licensed under the MIT or GPL Version 2 licenses and is therefore free to use, modify and/or distribute, but if you include Touch Punch in other software packages or plugins, please include an attribution to the original software and a link to this <a href="http://touchpunch.furf.com/" target="_blank">Touch Punch website</a>.</p>
